The code is not yet linted, because we should speak about the specific guidelines we'd like to define. That's why the CI build fails, currently.

Many thanks for submitting this! Although I'm not able to formally start a review as long as the PR is marked as draft, I might just add a preliminary one as a comment here:

First of all, generally, this looks good to me. There are a few minor remarks, though:

• Obviously, as you noted yourself in your last comment, we need to discuss the style guidelines being imposed. And we definitely should include @GonozalIX in that discussion.
• If this is supported by the spotless plugin, we might consider to downgrade a few of the guidelines to warnings, e.g. spotless should emit a warning for a violation of the particular rule, but the CI should not fail on this and a local run should not modify the file. This seems particularly relevant for any limitation of the length of code lines.
• You created this PR based on the v3_FileInfoImprovementAndRequestHandler branch and thus it implicitly depends on V3 file info improvement and request handler #157. There is no reason for this dependency. In fact, there is no reason for this change to wait for version 3. It could go into master right away instead. (Since you can't change the source branch of a PR in GitHub, this would require to create a new PR, though.)
• The config files eclipse-formatter.xml and eclipse-importorder.txt are cluttering the main directory. I would prefer them to be stashed away in a subdirectory like .spotless.